I don't have sure about this workflow being automated before fixing problems already known by the last version tried to be published.

I wasn't sure why it was commented out. Do you know what issue was there?

#227 is the one that commented it out, but seems unrelated. The commit specifically only has comment "turn off automated publishing for major bump". bb6a9ee

Is it possible to merge this? This repo has not had a release in over 1 year.

Yes, actually I'm the one looking and trying to take care of this repo.

I'm preparing to list the principal issues to be fixed and prepare the next major release for the lib.

Also, I want to publish the docs of swagger-jsdoc moving from the readme to a docusaurus page. If someone is interested in to help this feel free to contact me.

The good news is that npm has the latest version, but github is not updated with new release version (but tag v6.2.0 is there).

npm: https://www.npmjs.com/package/swagger-jsdoc
github: https://github.com/Surnet/swagger-jsdoc/releases/tag/v6.2.0